Fix System-CVE pair status not being set correctly #1926
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leSamo
force-pushed
the
pair-status-fixes
branch
from
d8dce87
to
2b12f04
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1926 +/- ##
==========================================
- Coverage 71.58% 71.57% -0.01%
==========================================
Files 117 117
Lines 2939 2938 -1
Branches 882 882
==========================================
- Hits 2104 2103 -1
Misses 835 835
☔ View full report in Codecov by Sentry. |
LiorKGOW
pushed a commit
to LiorKGOW/vulnerability-ui
that referenced
this pull request
Jan 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://issues.redhat.com/browse/VULN-2637
During some refactoring of selected items, the names of some parameters got changed which caused multiple issues while editing the status on the CVE detail page: